BBS Toolkit/BBS Toolkit.iso/gt_power/pvac161.zip/POWERVAC.DOC

Text File | 1991-03-03 | 26KB | 559 lines

     ┌────────────────────────────────────────────────────────────┐
     │    The following document is Copyright Cory Wright 1991    │
     └────────────────────────────────────────────────────────────┘

     █████                                  ██   ██  █████   █████
     ██  ██                                 ██   ██ ██   ██ ██   ██
     ██  ██  █████  ██   ██  █████  ██ ████ ██   ██ ██   ██ ██
     █████  ██   ██ ██   ██ ██   ██  ███ ██ ██   ██ ███████ ██
     ██     ██   ██ ██ █ ██ ███████  ██     ██   ██ ██   ██ ██
     ██     ██   ██ ███████ ██       ██      ██ ██  ██   ██ ██   ██
     ██      █████  ██   ██  █████   ██       ███   ██   ██  █████

     ┌────────────────────────────────────────────────────────────┐
     │  Verification and Access Control for GT Power 15.XX/16.XX  │
     │PowerVAC is Copyright 1990, Cory Wright. All rights reserved│
     └────────────────────────────────────────────────────────────┘

  ┌─────────┐
  │ Purpose │
  └─────────┘
    PowerVAC  is   designed  to  allow   PCBVerify,  a  seasoned   callback
    verification door for PCBoard, to work with GT Power v15/16 and provide
    users with  online verification while allowing  sysops to automatically
    verify each account on their BBS.

  ┌───────────────┐
  │ Compatibility │
  └───────────────┘
    PowerVAC has  been tested with  GT versions 15.01  through 16.00 of  GT
    Power by P&M Software. PowerVAC  has been tested under PCBVerify v3.10.
    TRC  Development and  Cory Wright  will only  provide support  to those
    running the  versions of the code  that PowerVAC has been  tested with.
    DDOSDOR.COM is  running on my BBS  and CHEKTIME is NOT  USED. PCBVerify
    actually drops  carrier, so GT cannot  be allowed to reboot  each time.
    DDOSDOR.COM has been included and should be loaded (instead of DOORMAN)
    one  time in  your AUTOEXEC.BAT  file. Other  users have  reported that
    DOORMAN WATCHDOG OFF works well too. Just remember that the door lowers
    DTR and drops carrier, so be sure that you don't let GT become aware of
    this and reboot!

  ┌────────┐
  │ Setup  │
  └────────┘
    Setting  up  PCBVerify  with  PowerVAC  is  relatively  simple. A setup
    feature has been  included with PowerVAC to assist you  in the setup of
    PCBVerify. In cases  dealing with the operations of  PCBoard within the
    PCBVerify documents,  these PowerVAC documents  will give you  specific
    instructions that  will override the  PCBVerify documents. Just  follow
    these steps to install PCBVerify and PowerVAC:

    1) Create a directory to place your PCBVerify files in. We'll call it
       C:\PCBV

    2) Unzip the PCBV310.ZIP archive  into C:\PCBV

    3) Read over the operation of PCBVerify  in PCBV310.DOC

    4) Place the  PVAC.EXE file into
       C:\PCBV

    5) Type   "PVAC  SETUP"   to  setup   PVAC  and  PCBVerify's
       configuration files. - You will be asked a number of questions that are
       fairly routine such as what baud rate to lock your port at (if any), if
       you  want to  allow callbacks  (as opposed  to verifications which will
       change a user's  access level if successful). When  you are asked where
       your PCBVerify files are, in this example, we would type C:\PCBV

    6) Create a file called UPGRADE.CNF in the PCBVerify directory you made
       (in our example: C:\PCBV).  It is a straightforward text file that
       consists of two columns and an infinite numbers of lines.

         Example:  VI
                   ZU
                   LA
                   C5

    This would tell  PowerVAC which levels to upgrade  to corresponding new
    levels.  For  example,  if  a  user  goes  into  the door with level V,
    PowerVAC  would tell  PCBVerify that   the user  needs to  be VERIFIED.
    PCBVerify would then  run, and PowerVAC would be  executed again, would
    check to  see if VERIFICATION  was successful and  upgrade the user  to
    level I,  but if it  wasn't, it would  leave them at  level V. The same
    thing  applies to  Z users  being upgraded  to U,  L to  A, and C to 5,
    according to the example file above. The  left column is the level of a
    user that needs to be VERIFIED, and  the right column (column 2) is the
    level to upgrade the user to if he is verified successfully.

      7) You will need to look over the PCBVerify docs to set up PCBVerify
         files that regulate verification, etc.  These examples are
         recommended starting blocks for building the files.

  ┌────────────────────────────────────┐
  │ PCBVNAL - Not allowed numbers file │
  └────────────────────────────────────┘
    This file will allow you to block numbers that PCBVerify will call

        615-531-8789,N
        615-531-8789,Y
        900-???-????,N
        900-???-????,Y
        ???-976-????,N
        ???-976-????,Y

    As you can see, wildcards are allowed in the phone numbers. Each number
    you wish  to block will  have two lines.  One for users  that enter the
    phone number  and say "Y"  to the long  distance question, and  one for
    those  that entered  the phone  number  and  answered "N"  to the  long
    distance question. I have blocked my  BBS phone number, all 900 numbers
    (which  can cost  considerably more  than normal  phone calls)  and any
    number starting  with 976- (which  are usually pornographic  numbers in
    the USA).

  ┌──────────────────────────────┐
  │ PCBVAL - Dialing format file │
  └──────────────────────────────┘
    This  file will  tell PCBVerify  how  to  dial out.  PCBVerify is  very
    flexible  and allows  calls to  be formatted  however necessary -- from
    dialing out of a PBX, to dialing on overseas lines, etc.

        615-???-????,N,N,A,"ATDT %2-%3"
        615-???-????,Y,Y,B,"ATDT 1-%2-%3"
        800-???-????,N,N,A,"ATDT 1-%1-%2-%3"
        800-???-????,N,Y,A,"ATDT 1-%1-%2-%3"
        ???-???-????,Y,Y,C,"ATDT 1-%1-%2-%3"

    More information is available in PCBV310.DOC. I will explain line 1. If
    the area  code starts with 615,  but is local (note  the 1st "N"), then
    PCBVerify will dial  the number in the format "ATDT  %2-%3" where %2 is
    the 2nd set  of 3 digits, and %3  is the final 4 digits  of the number.
    The 2nd "N" means "stay online and  return to the BBS". Since all local
    calls are free in my area, I  stay connected with the user and send him
    back to the board. The "A" designates the time frame to use as shown in
    PCBVTIME. As you  can see, anyone that is  long distance gets verified,
    then disconnected from the BBS with  the exception of 800 numbers which
    are free calls from the USA.

  ┌───────────────────────────────────┐
  │ PCBVTIME - Controls callout times │
  └───────────────────────────────────┘
    This file guides  PCBVerify as to when to call  out per the PCBVAL file
    on the previous page.

        A,0:00,24:00,0:00,24:00
        B,23:05,07:55,23:05,16:55
        C,17:05,07:55,17:05,23:56

    A is for local callers.  It will call them anytime.
    B is for in-state calls which are more expensive than out of state
      calls.  Therefore, I limit them to the lowest costs, which,
      according to the above example, run from 23:05 on a weekday night,
      to 07:55 the next weekday morning.  Then from 23:05 on Friday
      night to 16:55 on Sunday afternoon (when the rates go back up for
      some reason).
    C is for out-of-state calling which I do after 17:05 each evening
      until 07:55 the next morning and from 17:05 Friday until 23:56
      Sunday evening (at which time all other calls would fall into the
      Monday slot).

    Of course, I use US Sprint as my long distance carrier, so those of you
    on  AT&T  or  MCI,  etc,  should  change  your  times as needed... even
    validating long distance all day long is one alternative to look into!

  ┌───────┐
  │ Other │
  └───────┘
    There are other files that you may  need to set up. Please refer to the
    PCBVerify documents  for information on  dialing in Europe,  Australia,
    etc. I recommend the  format I've used above. It has been  in use on my
    BBS for over 4 months with 0 problems.


    8) Make a batch file. Decide what  door you want the verification to be
    on,  and make  the appropriate   batch file  (mine is  GTDOOR1.BAT). No
    converter is  needed -- PowerVAC  takes care of  it all. The  syntax is
    easy. According to  our example of files being  in C:\PCBV, GTDOOR1.BAT
    would look like this:

        c:
        cd\pcbv
        pvac in c:\pcbv\pcbv.cnf c:\pcbv\upgrade.cnf
        pcbv310 c:\pcbv\pcbv.cnf
        pvac out c:\pcbv\pcbv.cnf c:\pcbv\upgrade.cnf

    PowerVAC must run on either side of PCBVerify to be effective.

    9) Make  sure that this door  is overlayed! First, place  a /V:D on the
    command line that loads the BBS. If you  already have a /V:, add a D to
    it, like /V:EDL or /V:LD or  whatever. If you are running this software
    in your GTNLOGON.BAT file  (run when a new user logs on),  be sure an L
    is present in the /V: line.

    If you do not wish to overlay  your other doors, place an ampersand (&)
    after the door description for each door  you do not want to overlay in
    the  GTDDIR.BBS  file.  In  the   following  example,  door  1  is  the
    PCBVerify/PowerVAC  door  and  is  not  overlayed.  Doors  2 and 3 are.
    Remember, the PCBVerify/PowerVAC door MUST BE OVERLAYED.
  ┌────────────┐
  │ GTDDIR.BBS │
  └────────────┘
    V [PCBVerify]
    T [2] &
    T [3] &


    10) You're done!


  ┌─────────┐
  │ Example │
  └─────────┘
    An  example batch  file for  the door  is given  above, but  I also use
    PowerVAC/PCBVerify  when  a  new  user  logs  on.  It requires GTACCESS
    (another  of  my  programs  --  refer  to  the  OTHER.PRG  file in this
    archive), Force  Questionairre (FQUEST.EXE or  FQESTxxx.ZIP), a program
    by the OZ group in Australia, and MSGT by Mark Shasby of England. Other
    programs that perform the same task may be used, however.

    For your reference,  questionnaire 1 is for new  users, questionnaire 3
    is for GT Sysops. Both must be  called back. Here are the access levels
    I use and their explanations:

  ┌──────────────┐
  │ GTPASSWD.BBS │
  └──────────────┘
    GG [4:00,50,4:00]   CLASS DR,DN,UP,PR,MS,NL
    ; G is the standard GT Sysop access level
    HH [:30,20,:30]     CLASS DR,DN,UP,PR,MS,NL
    ; H is for GT Sysops that have filled out the quest, but not called back
    II [:30,20,:30]     PASSWORD DR,DN,UP,PR,MS,NL
    II [:30,20,:30]     CLASS DR,DN,UP,PR,MS,NL
    ; I is for GT Sysops that haven't answered the questionnaire.
    SS [:35,20,:35]     CLASS DR,DN,UP,PR,MS,NL
    ; S is the standard user level
    UU [:30,20,:30]     CLASS DR,PR,MS,NL
    ; U is class for those who have answered the questionnaire, but not
    ; called back.
    VV [:30,20,:30]     GUEST DR,PR,MS,NL
    VV [:30,20,:30]     CLASS DR,PR,MS,NL
    ; V is the starting level of all normal callers

  ┌──────────────┐
  │ GTNLOGON.BAT │
  └──────────────┘
    msgt level?
    REM According to level, either go to the GT SYSOP questionnaire,
    REM the normal questionnaire, or just callback if the questionnaire had
    REM been answered.
    if errorlevel 86 goto verify
    if errorlevel 85 goto callback
    if errorlevel 82 goto callback
    if errorlevel 73 goto gtsysop
    if errorlevel 72 goto callback
    if errorlevel 71 goto callback
    goto end

    :gtsysop
    gtgap drwy
    DOORWAY SYS /T:^C^K^P^X /O: /P:D:\GT\FQUEST.EXE /PPQUEST3.BBS /QQUEST3.BBS /AANSWER3.BBS /F /L /DI /UI
    gtaccess 3 I H 4
    msgt level?
    if errorlevel 73 goto hangup
    goto callback

    :verify
    gtgap drwy
    DOORWAY SYS /T:^C^K^P^X /O: /P:D:\GT\FQUEST.EXE /F /L /DV /UV
    gtaccess 1 V U 2
    msgt level?
    if errorlevel 86 goto hangup
    goto callback

    :callback
    cd\door\pcbv
    pvac in c:\pcbv\pcbv.cnf c:\pcbv\upgrade.cnf
    pcbv310 c:\pcbv\pcbv.cnf
    pvac out c:\pcbv\pcbv.cnf c:\pcbv\upgrade.cnf
    goto end

    :hangup
    dropdtr2
    goto end
    :end

    ** END OF BATCH FILE **

    Note that I do not let FQUEST upgrade the user, but GTAccess so that my
    answer file will get archived and my  users will be sent a message when
    they return  to the BBS.  With this powerful  batch file, I  have found
    that I can take care of all my  needs in one fell swoop. In fact, I use
    this exact batch file as my full GTDOOR1.BAT file so that if a new user
    gets disconnected, doesn't answer the questionnaire, or for some reason
    doesn't complete  the process, opening  door 1 can  pick back up  where
    they left off -- whether that be answering the questionnaire or getting
    called back. Modify the batch file to meet your needs.

  ┌────────────────────┐
  │ Sysop Notification │
  └────────────────────┘
    As of v1.60 of PowerVAC, the program will send a message to  the  sysop
    that contains the following information:

       User Name, hometown, times on, first date and time on, telephone
       Verification Outcome (Verified or not)
       Level adjustments, if any

    PowerVAC will automatically detect GT 15 or GT 16 message format.

  ┌────────────────────────┬─────────────────────────────────────┐
  │ Purifying the database │ A feature of the registered version │
  └────────────────────────┴─────────────────────────────────────┘
    If  you've instructed  PCBVerify to  do  so,  it keeps  a database,  or
    trashcan, of  numbers that have been  verified. It is a  good idea from
    time  to  time  to  purify  this  database.  To  do  so, simply run the
    purification function of PowerVAC in the following manner:

      PVAC PURIFY <path_to_PCBV_files>

    Of course, your  PCBVerify files should be in  their own directory, and
    you should point to such directory on the command line as shown above.

    PowerVAC will  process all of your  valid users names and  then compare
    them  one by  one to  the names  listed in  the PCBVVER  file. No phone
    numbers are  match or compared, just  names. This way, users  that have
    been deleted due to inactivity can call  back in and not be rejected by
    PCBVerify as  having been previously verified.  PCBVVER.BAK is a backup
    file of PCBVVER that PowerVAC creates for safety. After running PURIFY,
    the PCBVVER will have been cleaned,  PCBVVER.BAK will be the file as it
    stood  before being  cleaned, and  PURIFY.LOG will  exist in  your PCBV
    directory  that  logs  all  users  processed,  their  status, and other
    pertinent  data during  the purification  run. This  PURIFY.LOG file is
    appended to, so please be wary of its size.

  ┌─────────────────────────────────┐
  │ Entering Your Registration Code │
  └─────────────────────────────────┘
    Type "PVAC REGISTER" on the command line. A registration screen will be
    presented  where  you  will  enter  the  registration  name and CRC you
    received from TRC Development. Press 'Q'  to quit and save the changes.
    Upon exit,  if you have  properly registered the  program, it will  say
    "Registered to <your name>"; otherwise,  you will see  instructions on
    how to register your unregistered copy.

  ┌─────────────┐
  │ Limitations │
  └─────────────┘
    Until  PowerVAC is  registered, only  one limitation  is imposed.  Your
    callers  will only  have 5  minutes left  for their  current call  upon
    returning  to the  BBS. This  function is  not intended  to cripple the
    program, but to  allow you to evaluate the  software. PCBVerify has its
    limitation as well without being  properly registered. It will not keep
    a 'trashcan' log of numbers verified.  Registration can be done quite a
    few different ways  as outlined at the end of  this document and in the
    REGISTER.PV  file. By  the way,   the registered  version uses  a quick
    indexing file system to pick up the user's record faster on the way out
    of the door as well as a purification system as an added bonus.

    The  PURGE.EXE file  included with  PCBVerify v3.10  is INOPERABLE when
    dealing with GT. The PowerVAC software includes a purging function that
    will  purify the  PCBVVER database  to include  only those  numbers and
    names of valid users on your system.

  ┌───────────────────────┐
  │ Standard Demo License │
  └───────────────────────┘
    PowerVAC is a  Shareware program, and uploading of  the code to various
    bulletin  boards and  Shareware libraries  is encouraged;  however, the
    following limitations must be expressed:

    1) Under no circumstances should the code be modified or distributed in
    any other form than what it  was originally supplied by the author. The
    exception  is that  PowerVAC may  be compressed  using techniques other
    than ZIP, but the de-compressed form of PowerVAC must remain intact.

    2)  PowerVAC  may  not  be  redistributed  in  any  manner  other  than
    electronic file transfer unless cleared  with the author beforehand. No
    money   may   be   received   for   PowerVAC   except   to   cover  for
    telecommunications / service  charges, and in such a  case the cost may
    not exceed $5.00 US.

    PowerVAC may  be run for  a period of  time adequate to  allow for full
    testing of the software. If, after  running the code for one month, you
    decide not  to purchase the  registration license and  number, you must
    forfeit  this  license  and  remove  PowerVAC  from  operation  on your
    system(s). You may  keep a copy online for  distribution purposes only.
    PowerVAC may not be hacked or modified in ANY manner, including but not
    limited to  modifications leading to  the use of  features intended for
    registered users only. These features  are marked in this documentation
    under "Limitations." Also, the registration license is non-transferable
    and  under  no  circumstance  may  the  registration  number of another
    individual be used to enable these features or for any other purpose.



  ┌──────────────────────┐
  │ Registration License │
  └──────────────────────┘

    1) Once purchasing the registration license, limitations are lifted and
    the license is extended for life.  All future releases of PowerVAC will
    be made available,  registered, for no additional charge.  In any event
    that PowerVAC does not work properly, the author, Cory Wright, shall be
    liable for no  more than $10.00 US, and then  only if an honest attempt
    was made to contact the author and the situation remained unresolved.

    2) Registering  PowerVAC entitles the  registering party access  to The
    Rising Connection BBS or whatever  location support is maintained. This
    privilege is guaranteed  for as long as the  program is being developed
    and supported. Access may be terminated  if any rules or regulations of
    the bulletin board are broken by the registering party.

    3)  The registration  license is  non-refundable and  non- transferable
    without  prior consent  of the  author, Cory  Wright. The  name of  the
    bulletin board  may be changed if  evidence is given that  the board is
    truly changing names and in such a case the old registration number may
    not  be used  under any  circumstances. A  processing fee  may apply to
    change a BBS Name.

  ┌────────────┐
  │ Disclaimer │
  └────────────┘
    The author, Cory Wright, takes  no responsibility nor liability for any
    data loss, incurred  costs, or equipment damage resulting  from the use
    of PowerVAC,  unless evidence can  be given to  show that the  code was
    written  to  do  so  intentionally,  at  which  point, the author, Cory
    Wright, will be liable for no more than $10.00 US.

  ┌─────────────────────────┐
  │ Statement of Separation │
  └─────────────────────────┘
    Cory Wright, the author of PowerVAC, and Curtis Kowalski, the author of
    PCBVerify maintain separate copyrights  on our respective software, and
    separate BBS systems for support of  our respective software. In no way
    will Cory  Wright, PowerVAC, TRC Development,  or The Rising Connection
    BBS  be obligated  to support  the PCBVerify  product. Cory Wright, TRC
    Development, and The Rising Connection BBS will not burden Premier BBS,
    or  Curtis Kowalski  and his  respective interests,  with the technical
    support of the PowerVAC product.  We each remain separate entities with
    a common interest.

  ┌──────────────────────────────────────────────────────────────────────┐
  │   PowerVAC and all forms of PVAC.EXE from source to executable are   │
  │ property of Cory Wright.  GT Power is copyrighted by P & M Software. │
  │             PCBVerify is copyrighted by Curtis Kowalski.             │
  │     User License reprinted with permission from Curtis Kowalski.     │
  └──────────────────────────────────────────────────────────────────────┘

  ┌────────────────────────────┐
  │ Thanks where thanks is due │
  └────────────────────────────┘
    I must  thank  Curtis  Kowalski  for  the  great  program and his great
    attitude while working with me on the project.

    Thanks also to  Curtis for his permission to use  the same user license
    as that  of PCBVerify in  order to keep  the licenses as  consistent as
    possible. Small changes  have been made in this  document that apply to
    PowerVAC but not necessarily to PCBVerify.

  ┌──────────────────────┐
  │ A word on commitment │
  └──────────────────────┘
    Curtis  and  I  tend  to  share  the  same  viewpoints on the theory of
    Shareware. It is not only your duty to register the software if you use
    it on your BBS and find it of value, but also *our* duty to do the best
    job we possibly can in supporting  that software. In light of the legal
    mumbo-jumbo above, let me assure you  that The Rising Connection BBS is
    dedicated to  the PCBVerify/PowerVAC package.  TRC will do  its best to
    support GT users using the  software, but technical PCBVerify questions
    dealing with  bugs in the PCBV*.EXE  code itself cannot be  answered by
    us. Premier BBS  is the home board of PCBVerify,  and the sysop, Curtis
    Kowalski, will  be more than  happy to assist.  Latest versions of  the
    code are available on both BBS systems.

  ┌──────────────┐
  │ Registration │
  └──────────────┘
    Registration of the programs is  simple and may be accomplished several
    ways.

    1)  Call  The  Rising  Connection  BBS  at  615-531-8789  and  open the
    PCBVerify/PowerVAC registration  door. You may  charge the registration
    fee to  your VISA, MasterCard,  American Express, or  Discover card and
    receive the registration online! This  door will cover registration for
    both PCBVerify and PowerVAC as follows:

       $15 -> Registration of PCBVerify
       $10 -> Registration of PowerVAC
       --------------------------------
       $25.00 - Complete registration

    Please note that both programs are required for use on a GT BBS.

    2)  This door  is also  available  on  Premier BBS  at 615-522-2498  or
    615-522-2499.  Be  sure  that  you  open  the  door  that allows you to
    purchase BOTH PROGRAMS.

    3) Fill in  the registration form on the  next page and send it  to the
    address  shown. You  may use  a charge  card or  send a  check or money
    order. Please do not send cash.


===========================================================================
 TRC Development - Registration Form - TRC Development - Registration Form
===========================================================================

Name: _____________________________________________________________________

Address: __________________________________________________________________

         __________________________________________________________________

         __________________________________________________________________


Voice Number: ____________________        Data/BBS Number: ________________

BBS Name: _________________________________________________________________

Qty  Description                                           Fee in US$(each)
---  ---------------------------------------------------   ----------------

___  PCBVerify / PowerVAC Registration  [Single User       $25.00
     License - Standard]

___  Latest releases of both pieces of software on          $5.00
     a 5.25" 360k diskette.

___  Latest releases of both pieces of software on          $6.00
     a 3.50" 720k diskette.

Payment method:  CHECK   MONEY_ORDER          TOTAL COST:  $_______________
( Circle one - do not send cash )

If you are using a charge card, circle one:
---------------------------------------------------------------------------
 VISA           MASTERCARD           AMERICAN_EXPRESS           DISCOVER
---------------------------------------------------------------------------

CHARGE CARD CUSTOMERS:  We cannot process your order if you do not
include the expiration date of your card, and sign this form, authorizing
us to charge your account the TOTAL COST above.


Expiration date (Month/Year): _____ / _____

Authorized Signature:  ____________________________________________________

Name as it appears on card (please print):  _______________________________

===========================================================================
Please send this completed form and payment to:

Cory Wright
P. O. Box 53041
Knoxville, TN  37950-3041
===========================================================================

** END OF POWERVAC DOCUMENTATION ** Copyright Cory Wright 1991